Computerized sharing of digital asset localization between organizations

ABSTRACT

A computerized system and method provides for sharing digital assets among multiple different organizations in a multi-organization system, and further providing that one or more of localized digital assets can be assembled using digital assets, templates and rules specified by different organizations. Further, the various organizations can contribute and share digital assets with organizations, while controlling the localization of the asset with brand or other information both as specified by the provider organization and as specified by the user organization.

PRIORITY

This application is a continuation of U.S. patent application Ser. No.14/297,909, filed Jun. 6, 2014, which application claims priority toU.S. Provisional Patent Application 61/832,582 filed Jun. 7, 2013, U.S.Provisional Patent Application 61/833,795 filed Jun. 11, 2013, U.S.Provisional Patent Application 61/832,591 filed Jun. 7, 2013, U.S.Provisional Patent Application 61/833,826 filed Jun. 11, 2013, U.S.Provisional Patent Application 61/832,578 filed Jun. 7, 2013, and U.S.Provisional Patent Application 61/833,832 filed Jun. 11, 2013, all ofwhich are incorporated by reference herein in their entirety.

TECHNICAL FIELD

This application relates generally to data processing within anetwork-based system, and more specifically to systems and methods forsharing digital assets, such as information or marketing assets, amongorganizations.

BACKGROUND

The creation and sharing of digital assets, for example information ormarketing assets, can be a logistically challenging and/or inefficientactivity for many organizations. These challenges and/or inefficienciesmay be due to differences in the needs of the users for localization ofthe assets, due, for example, to differences in geographic locations,differences in the subject products or services, differences inchannels, differences in branding requirements and/or differences inlegal compliance requirements.

SUMMARY

A computerized system may receive digital assets and digital asset buildrules from a plurality of organizations wherein some or all of theorganizations can specify rules and information so that one or morelocalized digital assets can be generated for the particular needs ofone of the respective organizations using one or more of the digitalassets, and further wherein at least one of the localized digital assetsis created using build rules specified by at least two different ones ofthe organizations.

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments are illustrated by way of example and not limitation inthe figures of the accompanying drawings in which:

FIGS. 1-1, 1-2A and 1-2B illustrate an overview of digital asset sharingsystems and methods, according to an example embodiment.

FIG. 1-3A illustrates a simplified block diagram of amulti-organizational system 100 for creating, managing, sharing,publishing and/or distributing digital assets, according to one exampleembodiment.

FIG. 1-3B illustrates a process for building a localized digital asset,according to one example embodiment.

FIG. 1-3C illustrates a process used to build a localized digital assetby use of information obtained from various sources, according to oneexample embodiment.

FIGS. 1-3D-1 and 1-3D-2 illustrate multi-tenant aspects of the systemdisclosed herein, according to one example embodiment.

FIGS. 1-3E-1 to 1-3E-4 illustrate a digital assets library table,according to an example embodiment.

FIG. 1-3F illustrates database tables, for respective digital assetgroups, according to an example embodiment.

FIG. 1-3G illustrates a database table of asset build rules specified bya Provider or Client Organization, according to an example embodiment.

FIGS. 1-3H to 1-3J-3 illustrate an example embodiment of a shared asset,multi-skin asset sharing system.

FIGS. 1-3K to 1-3M illustrate an example embodiment of various exampleconfigurations of the systems and methods described herein.

FIG. 1-4 illustrates and overview of system components according to anexample embodiment.

FIG. 2 illustrates an environment for operating a mobile device,according to an example embodiment.

FIG. 3 is a block diagram illustrating a mobile device, according to anexample embodiment.

FIG. 4 is a block diagram illustrating a network-based system foraccording to an example embodiment.

FIG. 5 is a diagrammatic representation of a machine in the example formof a computer system within which a set of instructions for causing themachine to perform any one or more of the methodologies discussed hereinmay be executed.

DETAILED DESCRIPTION

Example systems and methods for digital asset management are described.In the following description, for purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of example embodiments. It will be evident, however, toone skilled in the art that the present invention may be practicedwithout these specific details. It will also be evident that the digitalasset sharing solutions described herein are not limited to the examplesprovided herein, and may include other embodiments not specificallydiscussed.

According to one example embodiment, there is described herein below amulti-skin, multi-organization, rights-based digital assets sharingsystem, for example used to share digital assets such as information ormarketing assets. In one example configuration, an Information ProviderOrganization is a for-profit or non-profit publisher of information,such as an online information resource/database, that is in the businessof supplying information to organizations such as the ClientOrganizations described herein. In this embodiment, the InformationProvider Organization employs the system to provide a plurality ofClient Organizations, such as law firms, accounting firms, or financialplanners, with a digital assets delivery platform that allows the ClientOrganizations to “localize” the Information Provider Organization'sdigital assets for the Client Organization's use. Further, in oneexample embodiment, the Client Organizations may either access and usethe Information Provider Organization's digital assets or manage and use“proprietary” digital assets introduced to the system by the respectiveClient Organization. The system, in one embodiment, is managed by theInformation Provider Organization, which in turn may provision eachClient Organization with its own account within the system. According toone embodiment, the Client Organizations account is provisioned with acustom user interface skin that displays the Client Organization'strademark, trade name and/or trade dress. Accordingly, the users fromeach Client Organization are provided the ability to view and use theInformation Provider Organization's digital assets, and further topublish the Information Provider Organization's digital assets, or itsown proprietary digital assets, localized with branding and otherinformation specified by the Client Organization. Thus, each ClientOrganization has the ability to move between Information ProviderOrganization's digital assets or their own proprietary library ofdigital assets specific to their needs.

According to another embodiment, the system may optionally limit thesharing of Digital Assets only to “peer-to-peer” sharing, wherein thereis no for-profit or non-profit Information Provider Organization that isengaged in the business of supplying content to other organizations(referred to herein also as a “commercial Information ProviderOrganization) such as the Client Organizations. Instead, in thisembodiment, an entity other than an Information Provider Organizationadministers the system, and the Client Organizations alone provideDigital Assets to be shared with other Client Organizations, and to belocalized by each respective Client Organization. In this capacity, eachClient Organization acts as a “peer” information provider organization.

The following terms are used herein, and should be interpreted inaccordance with the following definitions, the use of the terms in thespecification following the definitions, and other definitionsunderstood by those of skill in the art for the same term, provided thatsuch other definitions that are not inconsistent with the definitionsgiven herein.

Admin

Admin is a title given to users with Administrative capabilities in theAsset management and sharing system. Admins, in one example embodiment,have the ability to edit user permissions, utilize “Login As”functionality and have a greater level of access to digital assets ofthe Asset Library.

Asset

An asset is an umbrella term that refers to any digital file that can beused in internal or external communications efforts. Major types ofAssets include text, image, PDF, video, audio, podcasts. Any major mediafile type (e.g., JPG, DOC, MPEG, etc) can be used as an asset. Assetsare saved in and accessed from the Asset Library.

Asset Groups

Asset Groups, in one example embodiment, allow admin users to managewhich sets of assets an Organization and/or user within an Organizationis allowed to access when they customize emails or other materials.Organizations and/or Users can belong to one or multiple Asset Groups.

Asset Group Admin

Asset Group Admin functions, in one example embodiment, help manage howassets are stored and which Organizations or Users can access them. Inone embodiment, a system or organization admin can add, remove or renameasset groups. An Asset Group can be created by an Information ProviderOrganization or, in one example embodiment, also be created by a ClientOrganization, either of which, respectively can specify which ClientOrganizations can access the Asset Group. Client Organizations can inturn specify which of their Users can access Asset Groups available tothe Client Organization.

Asset Library

In one example embodiment, all assets are stored in the Asset Library.

Client ID

The client ID, in one example embodiment, is an optional informationalassignment given to assets to assist in identifying and narrowing thesearch for assets.

Client Organization

In one example embodiment, a Client Organization is an organizationprovisioned by the Information Provider Organization in the system bywhich the Client Organization, for example, can share Digital Assetsprovided by the Information Provider Organization, or in an optionalalternate embodiment, share Digital Assets with other ClientOrganizations.

Custom Dictionary

In one example embodiment, the Custom Dictionary allows a user to addwords into the system that are specific to an Organization and may notbe recognized in an English Dictionary. These words may be brand namesor product offerings, etc. Adding them to the Custom Dictionary willstreamline the spell check process for users.

Expiration Date

According to another example embodiment, users can activate and setexpiration dates for any asset to determine when they will be accessibleto users in the system.

Information Provider Organization

In one embodiment, the Information Provider Organization is anorganization that publishes Digital Assets and, optionally, in oneexample embodiment, also administers the system for sharing DigitalAssets, as described further herein.

Image Assets

Image Assets, are any files saved as images, for example for use inemail or PDF customization. In one example embodiment, these assets maymake up the sections of the Template Zones to which they are assigned.File types can include but are not limited to JPG, GIF, PDF, PNG andEPS.

Image Info

According to an example embodiment, Image Info displays basicinformation about the asset including its ID, Title, Content, expirationdates and Text Asset type. This Image Info may comprise the asset anddetermine how it is used in a template.

Keyword(s)

In one example embodiment, by default, keywords are be used in filteringboth template options and Asset library searches. Keywords are assignedto assets to assist in organization and to simplify searching. Keywordsare organized in groups to easily assign an asset to multiple relatedkeywords.

Keyword Admin

In an example embodiment, assets may be assigned categories in Assetmanagement and sharing system. Categories are then organized intokeywords. Keywords make the search process easy, allowing users to findmaterials they're looking for quickly in the Asset library or whileusing a template. The Keyword Admin section may allow the admin to editthe categories and keywords.

Localize

In example embodiments, Digital Assets are customized to includeLocalizations such as, but not limited to, localizations desired due todifferences in geographic locations, differences in the organizationsusing the Digital Assets, differences in the subject products orservices, differences in channels, differences in branding requirementsand/or differences in legal compliance requirements.

Login As

In another example embodiment, the Login As functionality allows anadmin to login as a user to monitor activity, or operate the selecteduser's account as the user.

Multi-Tenant System

Multitenancy refers to a software architecture where a single instanceof the software runs on a server, serving multiple client organizations(tenants). With a multitenant architecture, a software application isdesigned to virtually partition its data and configuration, and eachclient organization works with a customized virtual applicationinstance.

Organization Hierarchy

In one example embodiment, the Organization Hierarchy refers to theuser's place within the Organization tree of system permissions. Forexample, employees/users, in one example embodiment, are grouped beneaththeir supervisor. Groups may be nested hierarchically, meaning head ofthe organization is at the top of the hierarchy and subordinates followaccording to rank.

Print Vendors

In one example embodiment, Print Vendor information is stored for use inPrint-on-Demand orders for an Organization's preferred printers.

Template(s)

In one example embodiment, Templates serve as architectural patterns toassist in building communication pieces such as emails and PDFs. Theyprovide a consistent foundational model with designated Template Zonesinto which various assets can be placed. Templates promote consistencybetween communication pieces by providing a limited number of specified,customizable variables.

Template Zone

In an example embodiment, each template has zones assigned to organizeasset placement. You can assign assets to particular Template Zones,insuring that only relevant assets are available to users whencustomizing materials and emails.

Text Asset

In an example embodiment, Text Assets are any text materials. Thisincludes headers, greetings and articles. These assets may be accessedby users in templates when customizing emails or PDFs to make up thepieces of the template zones to which they are assigned.

Text Type

In another example embodiment, Text Type identifies the nature/type oftext of which a text asset is comprised. This can be any kind of text,including greetings, articles, headers, body copy, calls to action,secondary copy, etc. Text type assists in locating and placing theappropriate type of text in template zones.

User Admin

In an example embodiment, the User Admin function allows admins to editor review system, asset, organization or user information, for exampleuser roles, asset groups, the user's place in the OrganizationHierarchy.

User Details/User Info

In one example embodiment, these personal and contact details may beused to populate fields in custom email and PDF templates.

User Interface (UI) Skin

In an example embodiment, the UI Skin describes or defines theaesthetic, visual, primarily cosmetic aspects of a UI, as opposed tofunctional elements, for example but not limited to graphical elementssuch as colors, fonts, formatting and brand elements such as tradenames, trademarks or trade dress that alter the look and feel of thefunctional user interface elements. Skinning may be implemented with amodel-view-controller architecture.

User Roles

In an example embodiment, each User in the system must be assigned auser role. This may determine their permissions and capabilitiesthroughout the system.

Referring now to FIG. 1-1, there is illustrated an overview of a digitalasset sharing system according to one example embodiment. System 100includes one or more data structures and computer programs to hold,store, manipulate, display and otherwise use various kinds of data usedto automate various digital asset management, authoring, localization,distribution, publication or other asset sharing or management tasks. Inone example embodiment, data structures and programs are represented bydata and modules that include digital assets in the form of informationassets 105, such as marketing materials, customizable template module116, list management module 115, campaign management module 120,marketing material depository module 125, business rules, policies, usermanagement module 130, measurement, and analytics and big data module135.

A front-end web portal 140 provides a graphical user interface for useby various constituencies, including corporate and product marketingpersonnel, creative services personnel, field marketing personnel, andpersonnel in distributed sales, channel sales and distribution partners.A back-end administration portal 145 provides access to systemsadministrators to provide a variety of system configuration functions,as explained herein below.

In addition, system 100 connects to a variety of services 150 used todistribute digital assets, such as information content or marketingassets, including e-mail, print on demand, SMS text, social media, anddirect marketing services. Also, system 100 interfaces with variousother systems 155 including customer relationship management systems,point of sales systems, social media systems, print systems, e-mailsystems, direct mail systems, fulfillment systems and translationsystems.

Referring to FIG. 1-2A, there is illustrated an overview of the assetmanagement control applied to individual digital assets 160. Businessrules and access privileges 162 are used to control access to assets 160on multiple levels or dimensions 164, based on a defined organizationalhierarchy, privileges of individuals in that hierarchy, the geographiclocation of an organization or user, language requirements, local legalrules and regulations, and/or specific restrictions applied toindividual assets 160.

According to one example embodiment illustrated in FIG. 1-2B, the system100 allows for multiple levels of administration of asset management,wherein a first administrative user may establish a group of individuals174 in a first organization, one or more of which may in turn beauthorized to establish one or more subgroups of users 176, and so on tocreate even lower levels of hierarchy. The privileges of each groupand/or individual to use digital assets 160 in the system 100 may bespecified. Accordingly, a first set of digital assets 160 for exampleassets A1 and A2, may be authorized for use by a first group as a whole,but only a portion of that authorization may be passed onto individualmembers of the group by a person responsible for managing the firstgroup, for example, by individual I-1 who provides access to asset A1.In addition, a member of the first group, having privileges to the firstset of digital assets 160, may in turn create his or her own subgroup,and selectively pass the privileges to use individual ones of the firstset of assets 160 to individual ones of that subgroup.

FIG. 1-3A illustrates a simplified block diagram of the system 100,according to an example embodiment, wherein at least one of a pluralityof Organizations 201-1, 201-2, 201-3 . . . 201-n (collectively orindividually referred to herein as Organizations 201), acts as anInformation Provider Organization 201-1 and, in one example embodiment,is a publisher of digital assets 160, such as online information. Inthis example embodiment, for example, the Information ProviderOrganization 201-1 may provision Client Organizations 201-2, 201-3, etseq. (collectively “Client Organization(s) 201-2”) with rights to usesystem 100, herein referred to as an “account” within the system 100,and authorize such Client Organizations 201-2 to access and/or usedigital assets 160 introduced by the Information Provider Organization201-1. These digital assets 160, in one example embodiment, are storedin a data storage system as described further below, and are organizedinto a plurality of Asset Groups 202-1, 202-2, 202-3 . . . 202-n(collectively or individually referred to as Asset Groups 202). Inanother example embodiment, Client Organizations 201-2 are not tenantswithin the system 100, but share an account with the InformationProvider Organization 201-1. In still another example embodiment, anorganization or user other that the Information Provider Organization201-1 administers the system 100, for example to provision InformationProvider Organizations 201-1 or Client Organizations 201-2.

According to another example embodiment, the Client Organizations 201-2may also introduce their own proprietary digital assets 160 into system100, which may be stored in one or more of the Asset Groups 202, and usethose assets on a proprietary basis. Accordingly, in one exampleembodiment, the Client Organization 201-2 may thus either use digitalassets 160 provided by the Information Provider Organization 201-1, oruse their own proprietary digital assets 160. In yet another exampleembodiment, Client Organizations 201-2 may also share its ownproprietary digital assets 160 with other Client Organizations 201-2.

Accordingly, in one example embodiment, one or more of Asset Groups 202contains digital assets 160 provided by the Information ProviderOrganization 201-1, and other Asset Groups 202 contain proprietarydigital assets 160 provided by the Client Organizations 201-2. TheInformation Provider Organization 201-1 in this example embodiment maybe a for-profit or non-profit digital assets 160 publishing organizationsuch as, but not limited to, a publisher of scientific, business, legal,or medical data. Such information or data may, in some but not allexample embodiments, be sold or licensed, for example, on a for-profitor non-profit basis, using a business-to-consumer orbusiness-to-business distribution model. For example, the publisher maypublish or distribute legal information such as treatises, statutes,case, case notes and legal analysis. According to still another exampleembodiment, Client Organization 201-2 may be a professional organizationsuch as a private practice law firm or law department in a corporation.

An Access Rights module 204, in one example embodiment, maintains accessrights data, described in more detail below, that specifies thepermitted access and uses by individuals in each of the ClientOrganizations 201-2, such as administrators or end users of the digitalassets. An Asset Template Module 205 maintains Template data, describedin more detail below, that specifies Templates to be used to assembleassets for use Organizations 201. An Asset Build Rules Module 206maintains build data and rules that include, for example, rulesspecified both by an Information Provider Organization 201-1 and by aClient Organization 201-2.

An Asset Build Module 207, in one example embodiment, receives requestsfor assets from users at one or more of the Client Organizations 201-2,and, using information obtained from the Access Rights Module 204, AssetTemplate Module 205 and Asset Build Rules Module 206, performs theprocess illustrated in FIG. 1-3B-1: 1) determines 209-1 which assets theuser has rights to access, and optionally, what operations or uses theuser may perform on or with the asset, 2) identifies 209-2 the rules anddata to be used to build a localized digital asset (e.g., an asset 160that is ready for use), 3) identifies 209-3 the template specified to beused to build the localized asset, 4) builds 209-4 the localized digitalasset, and 5) displays 209-5 the localized digital asset 210 to the userat the respective Client Organization 201-2, who in turn may use theasset 160 as permitted. According to one example embodiment, asillustrated, the localized digital asset 210 includes digital assets210-1 retrieved from the asset library, template structure 210-2retrieved from the Template Module Data, brand or other informationvariables 210-3 specified by an Information Provider Organization 201-1(also referred to as a “provider” in FIGS. 1-3B and 1-3C) and/or by aClient Organization 201-2, that may use or “consume” one or more of thedigital asset 160 and the localized digital asset 210 (also referred toas a “consumer” in FIGS. 1-3B and 1-3C) in the asset build rules.Accordingly, in one embodiment, the localized digital asset 210 isformed using a digital asset 160 from the asset library that is at leastin part “non-localized.” This digital asset 160 is then “localized” (orfurther localized if the asset 160 already has some localization) withbranding and/or other information specified by the Information ProviderOrganization 201-1 and/or the Client Organization 201-2, such that thedigital assets 160 from the asset library. In one example embodiment,the digital assets 160 provided by the Information Provider Organization201-1 may have no localization, and all localization is provided by theClient Organization 201-2.

In one example embodiment, where the localized digital asset 210 isintroduced into system 100 by the Client Organization 201-2, the digitalassets 160, templates and build rules may be provided entirely by theClient Organization 201-2, such that localization of the digital asset160 is entirely or primarily defined by the Client Organization 201-2.Alternatively, digital assets 160 introduced into system 100 by a ClientOrganization 201-2 may be localized using at least some templates orbuild rules provided by the Information Provider Organization 201-1.

For example, as illustrated in FIG. 1-3C, the process outlined above maybe used to build a localized digital asset 210 by combining 214 anon-localized (or at least partially non-localized) digital asset 210-1(e.g., the digital asset 160), contributed by either an InformationProvider Organization 201-1 or Client Organization 201-2 (termed a“provider Organization” in some references herein), and kept in an assetlibrary (discussed further below), with Template information 210-2 andwith brand or other information 210-3 specified by build rules specifiedor adopted by an asset consuming Client and/or an Information ProviderOrganization 201-1. According to another example embodiment, the ClientOrganization 201-2 or Information Provider Organization 201-1 mayspecify both the Template information and the build rules.

According to one example embodiment, the provider Organization hasadministrator access to system 100 to specify combinations of digitalassets 160, asset templates, and build rules, wherein the providerOrganization may specify assets that are to be used by a ClientOrganization 201-2. Moreover, the Client Organization 201-2, in oneembodiment, has access to administrator functions on system 100 tospecify rules on how to add additional localization informationvariables to an asset, such as adding the Client Organization's 201-2branding information or other information. For example, in the case theClient Organization 201-2 is a service firm, such as a law firm, thefirm may establish rules that specify a firm name and/or logo to beadded to an asset, and/or for example contact information for the firm,and/or for example legal notices that may be advisable or required byapplicable ethics rules or consumer protection laws. According to oneexample embodiment, the Information Provider Organization 201-1 mayestablish a template that includes its desired brand information in thetemplate, or it may add brand or other information to a template usingbuild rules it specifies.

Referring now to FIG. 1-3D-1 and FIG. 1-3D-2, there is illustrated anexample embodiment of system 100 with multi-tenant capabilities. Asshown in the example embodiment of FIG. 1-3D-1, system 100 is configuredto provide access to Organizations 201 using a software as a service(SAAS) model. In one example embodiment, the Information ProviderOrganization 201-1 administers a multi-tenant embodiment of system 100and provisions and administers tenant accounts 211-1 . . . 211-n in thesystem 100 for each Client Organization 201-2. In this exampleembodiment, each Client Organization 201-2 has its own tenant account,and the Information Provider Organization 201-1 shares its digitalassets 160 with the Client Organizations 201-2 from its own tenantaccount to the respective tenant accounts of the Client Organizations201-2.

In an alternate embodiment, the Information Provider Organization 201-1and the Client Organizations 201-2 share a single tenant account, andeach Client is provisioned as a sub-organization so that the InformationProvider Organization's 201-1 digital assets 160 are shared within asingle tenant account with the Client Organizations 201-2. In thisembodiment, multiple Information Provider Organizations 201-1 may eachadminister their own tenant account and in turn provision ClientOrganizations 201-2 as sub-organizations within their own tenantaccount.

In either of the above configurations, Information Provider Organization201-1 or Client Organizations 201-2 may have respective members andusers, such as their employees or agents, who are registered as users inthe respective tenant account. Each member has a profile thatdetermines, at least in part, the rights the user has to access and workwithin the respective tenant account 211, and in turn with the data 213in data storage system 203. Data 213 may be digital assets 160 madeavailable to it by an Information Provider Organization 201-1, or in analternate embodiment, also by another Client Organization 201-2 withinthe same tenant account or in another tenant account, depending on theconfiguration.

Various database tables are used, in one example embodiment, to enableor perform the various software functions and processes describedherein. Referring now to these tables, FIG. 1-3E-1 illustrates a userprofile table 219 in a database according to an example embodiment. Userprofiles are identified in the table 219 by a User ID, a name for theuser, the Organization ID for the Organization the user belongs to, anduser profile information such as but not limited to access rights forthe user, rights with respect to use of specific assets 160 or functionsof the system 100, and other user-specific information.

FIG. 1-3E-2 illustrates a digital assets library table 220 in a databaseaccording to an example embodiment. Assets 160 are identified in thetable 220 by an Asset ID, and the table identifies an Organization 201,using an Organization ID, that is the asset provider (e.g., either anInformation Provider Organization 201-1 or a Client Organization 201-2)for the asset 160, a title for the asset 160, a storage location for theasset 160, the Groups that the asset 160 has been assigned to, and otherasset information as necessary or optional.

FIG. 1-3E-3 illustrates a template table 221 in a database according toan example embodiment. Templates are identified in the table 221 by aTemplate ID, a name for the template, a storage location for thetemplate, and other template information as desired.

FIG. 1-3E-4 illustrates a user interface (UI) skin table 225 in adatabase according to an example embodiment. UI skins are identified inthe table 217 by a UI skin ID, a name for the skin, the Organization IDof the organization for which the skin is to be used (or alternatively,skins may be assigned to specific users), a storage location for theskin, and other UI skin information as desired.

FIG. 1-3F illustrates database tables 250-1 to 250-n, for respectivedigital asset groups 202 according to an example embodiment. Each assetGroup table specifies one or more digital assets 160, identified by anAsset ID, that are within the Group. For each asset 160 in the Group,there is indicated the Provider or owner of the asset 160, whichOrganizations 201, and in turn their respective users, that arepermitted access rights to the assets 160 in the Group, and optionally,the rights that each Organization 201 has to use the respective asset160 they have access to. As illustrated further below, an Organization201 is provided an administrative interface through which to createGroups of assets 160 from an asset library created by or accessible tothe Organization, for example assets 160 added to the library by theOrganization. As noted, in various embodiments, the Information ProviderOrganization 201-1 may be the only provider of digital assets 160 to beshared and/or used in the system 100, or Client Organizations 201-2 mayalso contribute digital assets 160 to be shared and/or used in thesystem 100.

FIG. 1-3G illustrates a database table 222 of asset build rulesspecified by a Provider of the digital assets 160, such as anInformation Provider Organization 201-1 or a Client Organization 201-2,according to an example embodiment. Build rules may include a set ofrules and information variables for each asset 160 in a Group madeavailable to users in Organizations 201. Such rules and informationspecify, for example, a Template to be used for the asset 160, whereinthe Template may be the same for all Organizations using the asset 160,or the rule may specify different Templates depending on theOrganization of the user using the asset 160. Further, the rules mayspecify branding or other information for building the asset 160, suchthat this information may be applicable to all users no matter whichOrganization they are in, or such that this information is specific tothe users in a particular Organization only. As such, the asset buildrules provide an Organization the ability to localize an asset 160 foruse by its own users in a first way, localize it for users of adifferent Organization in another way, and localize it for yet anotherdifferent Organization in still another different way. Furthermore, therules are in no way limited to these examples. For instance, the rulesmay further specify different asset builds for users not only based ontheir Organization, but also based on their location or other attributesof the user, such as a user's expertise level.

Build rules may also include a set of rules and information for eachasset 160 in a Group made available to users in the Client Organization201-2. According to one example embodiment, the Template for the buildis specified by the Organization providing the asset 160, and the ClientOrganization 201-2 using the asset 160 defines rules for branding orother information to be added to the Template, in a Template Zone, tobuild the asset 160. In one embodiment, such rules or information areapplicable to all users in the Client Organization 201-2, or optionally,such that this information is specific to particular users only. Assuch, the asset build rules provide the Client Organization 201-2 theability to add additional localization information. Furthermore, therules are in no way limited to these examples. For instance, the rulesmay further specify different asset builds for users not only based ontheir Organization, but also based on their location or other attributesof the user, such as a user's expertise level. Alternatively, theOrganization providing the asset 160 may allow the Client Organization201-2 to specify a Template to be used for the asset 160, and for someof the localization information for the template to be created based onbuild rules established by the Organization providing the asset 160 foruse by the another Organization.

Referring now to FIG. 1-3H to 1-3J, there is illustrated an exampleembodiment wherein the Information Provider Organization 201-1 of thesystem 100 is a legal information provider, dubbed the “Legal ContentCompany” in the illustrations. FIG. 1-3H illustrates a user interfacewith a skin 230-1 that is presented to the Legal Content Company. FIG.1-31 illustrates a UI view into an organizational hierarchy whereingroups of users, within one or more Organizations, are afforded accessto a digital assets library provided the digital assets company areorganized by region 230-2, for example countries, territories, statesand provinces. In the example embodiment, under the state of Minnesota,there is illustrated a Group of users belonging to the Smith & Jonesfirm, and also a Group called Real Estate Lawyer. The UI of FIG. 1-3J-1,there is illustrated a UI skinned 230-3 for the Smith & Jones firm. Inthis example, the Smith & Jones firm may act as a user organization,using digital assets 160 localized in accordance with templates andrules specified by the digital assets provider company that providesdigital assets 160 to various user organizations such as the Smith &Jones firm, and also localized with brand or other information based onbuild rules specified by the Smith & Jones firm, or, in an alternativeembodiment, also using templates specified by the Smith & Jones firm.

Further, as also illustrated in the above described UI, and FIG. 1-3J-2,is dependent on the Organization to which the user belongs. As forexample illustrated in the process 233 of FIG. 1-3J-2, the UI skin 230-1or 230-3 is determined by system 100 by first receiving 233-1 the logincredentials for a user, next determining the UI skin ID for the user,based on the Organization to which the user belongs, for example asdetermined from table 217, and determining 233-2 the skin for thatOrganization from the table 1-3E-4, obtaining 233-3 the skin informationfrom data storage, and then generating 233-4 the UI skin to present tothe user, for example in this example, a UI skin that shows the brandingfor the Smith & Jones firm, or the Information Provider Organization201-1 skin for a user logging in with that skin specified. For example,as illustrated in FIG. 1-3J-3, users 1, 2, . . . n, from respectiveOrganizations 1, 2, . . . n, are each presented with a different UI skin1, 2, . . . n, respectively, in the event that each Organization has itsown unique skin, as determined by the process 233, which in one exampleembodiment is implemented using a computer program executing in thesystem 100.

Accordingly, as described above, and as shown in FIGS. 1-3K, 1-3L and1-3M, there is provided a system 240 that, in one embodiment shown inFIG. 1-3K, is configured such that an Information Provider Organization201-1, such as a commercial provider, that may also optionallyadminister and host the system, introduces digital assets 160 into thesystem 100, and Client Organizations 201-2, and in particular in oneembodiment organizations that are peers of one another, are allowed tolocalize those assets 160 for their own use. For example, the peerClient Organizations 201-2 may all be law firms or accounting firms orany other type of organization that would have a common interest in aparticular type of digital asset 160 to use in its business. In oneconfiguration of the embodiment of FIG. 1-3K, only the InformationProvider Organization 201-1 is allowed to share digital assets 160 withthe Client Organizations 201-2, and the Client Organizations 201-2 mayestablish their own build rules and templates for localization of thedigital assets 160.

Alternatively, in another embodiment illustrated in FIG. 1-3L, thesystem is configured without a host Information Provider Organization201-1, and is operated only with peer Client Organizations 201-2 thatboth introduce digital assets 160 into the system for their own use andlocalization, and optionally as well share their own assets 160 withother peer Client Organizations 201-2, who may localize the shareddigital assets 160 from other peer Client Organizations 201-2 for theirown use.

Or, alternatively, in another embodiment shown in FIG. 1-3M, the system100 is configured to allow both the Information Provider Organization201-1, such as a commercial provider, and the peer Client Organizations201-2 to introduce and share digital assets 160 with the otherOrganizations.

In another example implementation of FIGS. 1-3K, 1-3L and 1-3M, theClient Organizations 201-2 are only partially peers of one another inthe sense that their interest in the digital assets 160 may onlypartially overlap, or not be in the same industry or business, butnonetheless share an interest in the same type of digital assets 160.

Further, for example as described above with respect to in FIGS. 1-3Band 1-3C and elsewhere herein, the localization of a digital assets 160may be performed using build rules specified by one or both of the userof the Digital Asset or the provider of the digital assets 160, toprovide shared control over localization of a digital asset 160 betweenmultiple Organizations. Accordingly, either or both of the Organizationsmay specify the template or localization criteria or content for thedigital assets 160 being localized.

Referring to FIG. 2, there is illustrated an overview of an exampleembodiment of various modules of the system 100 that may be used to setup and maintain the system data structures and configuration required tosupport the various functions of the system for users. Modules 180 to193 accordingly provide both computer program instructions that areexecuted on a computer platform such as those described in more detailbelow, and data structures to organize and store data created by orloaded into the system by users, such as configuration data or assetdata, such as digital assets 160.

A User Manager module 180, according to one example embodiment, allows auser to browse a list of all users or search by their first or lastname, and to add, delete or edit users, including the following methodsand functions: i) locate the desired user in the User Directory; ii)view their User Details; iii) edit User Details; iv) delete a User; v)add a new user; and/or vi) assign a Login/User Name and a Password.

A Profile Manager Module 182, according to one example embodiment,displays basic contact information about a user, and allows for entry oredit of profile information. These details may be used to populatefields in custom email and PDF templates. According to one exampleembodiment, up to three personal images or logos may also be uploadedfor use in selected templates. According to one example embodiment, theProfile Manager Module has a configurable localization setting for eachuser that allows the administrator to set the language for the user.When the user logs in, the system automatically changes the GUI oneither the back-end portal or the front-end portal, depending on whichinterface the user is accessing, to the language/localization settingfor that user.

Asset Groups module 183, according to one example embodiment, allows auser to manage which sets of digital assets 160 a user is allowed toaccess. Users may belong to one or multiple Asset Groups 202. An adminuser, for example, may assign which Asset Groups 202 should have accessto this digital assets 160. Module 183 also allows for adding a user toan Asset Group 202, for example by granting the user access to thedesired group. In addition, this module and corresponding GUI alsoallows Admin Users to assign Users access to functionality for thespecified Asset Groups 202. For example, according to one examplemethod, the user may be granted or denied rights to: i) download ororder digital assets 160; ii) customize Email or materials/digitalassets 160; iii) manage their Address Book or Profile; and/or iv) postto Social Media channels.

Assign Admin Rights module 185, according to one example embodiment,manages admin rights and controls access to specific functionality. Forexample, the following rights, are available to be assigned: i) managingthe Asset library, Template Assets, Keywords and Asset Groups 202 forthe specified Asset Groups 202; ii) grant a user access to login asanother user, the rights to run drilldown/summary reports, manage printvendors and manage the hierarchy; iii) additional permissions allow auser to manage the Message Center (on the Home screen), manage theCustom Dictionary, and manage Asset Specific Vendors; and/or iv) theright to grant users the same admin rights to others users in theirhierarchy.

Print Vendor Admin module 186, according to one example embodiment, hasthe ability to add or edit Print Vendor information stored in the systemfor user orders.

Asset Group Admin module 187, according to one example embodiment, is anorganizational function to help manage how a user's digital assets 160are stored and who may access them. This module allows an Organizationadmin to add, remove or rename the system asset groups 202.

Keyword Admin module 188, according to one example embodiment, providesthat digital assets 160 are assigned categories in the system, and thenorganized into keywords. Keywords assist with the search process in theAsset Library or sorting of digital assets 160 within a customizabletemplate. By default, keywords may be used in filtering both templateoptions and Asset Library searches. A Template Only preference may beset to allow a user to determine if a keyword or keyword category mayonly be used when filtering digital assets 160 used in atemplate—meaning they will not be available in the Asset Library.

The Asset Library Admin module 189, according to one example embodiment,allows admin users to manage digital assets 160 accessed by users in theAsset Library. A user may search by Title, Client Item ID, Asset Groups202, Categories or Expiration Date. Asset Details contains all of theasset's digital assets and settings. This information assists the Systemwith the management of the digital asset 160. New digital assets 160 mayalso be added by the module 189. When adding a new digital asset 160, auser, in one example embodiment, assigns all details of the digitalasset 160. Also, a user may delete the digital asset 160—if it has notbeen used in a template. Digital assets 160 information may include, inone example embodiment, basic information about the digital assets 160including its an Asset ID, Title, Description, expiration dates, anddownload availability. The asset 160 start and expiration dates may beused to determine when the digital assets 160 will be accessible bysetting a start or expiration date.

The Text Admin module 190, according to one example embodiment, managesText Assets which includes headers, greetings, articles, and body copy.When customizing emails or PDFs, these digital assets 160 may beaccessed by users in templates. The following example functions andmethods are provided for this purpose: i) a search filter allows a userto search by Title, Asset ID, Asset Groups 202, Templates, Categoriesand Expiration Date; ii) asset details may be displayed and/or edited;iii) new digital assets 160 may be added; iv) digital assets 160 may bedeleted; v) a digital asset 160 may be associated with a public URL oran Asset Library URL; vi) a digital asset 160 may be linked to otherdigital assets 160 already stored in the Asset Library. For example, auser may want to connect a specific article or white paper with a user'semail headline or paragraph of text—this may help provide a particulardigital asset 160 to be included with a user's text asset, as a link tothe PDF; vii) a user may manage the templates where the text asset willbe used; viii) a user may assign digital assets 160 to particularTemplate Zones, insuring that only relevant digital assets 160 areavailable to users when customizing materials; and ix) keywords may beassociated with each digital assets 160.

The Image Admin module 191, according to one example embodiment,controls Image Assets, which are any files for use in email or PDFcustomization. These digital assets 160 make up components ofcustomizable templates to which they are assigned. The following examplefunctions and methods are provided for this purpose: i) search for adigital asset 160 by Title, Asset ID, Asset Groups 202, Templates,Categories and Expiration Date; ii) viewing or editing an image asset;iii) adding or deleting an Image asset; iv) display, add or edit basicinformation about the digital assets 160 including its ID, Title,Content, Expiration Date and Text Asset Type (this Image Info maycomprise the digital asset 160 and determine how it is used in atemplate); v) manage the templates that the Image Asset will be used in,for example assign an image asset to particular Template Zones, insuringthat only relevant digital assets 160 are available to users whencustomizing materials; vi) assign which Asset Groups 202 should haveaccess to this digital asset 160; vii) assign the keywords associatedwith each image asset.

The Organization Hierarchy module 192, according to one exampleembodiment, manages a list of users grouped the way they are structuredin the organization. The hierarchy is beneficial for Reporting andLogin—as structure. The following example functions and methods areprovided for this purpose: i) create/edit Hierarchy, wherein theHierarchy allows a user to establish the organizational structure whereusers will be assigned.

The Custom Dictionary module 193, according to one example embodiment,allows a user to add words into the system that are specific to a user'sorganization and may not be recognized in an English dictionary. Thesewords may be brand names, product offerings, etc.

Example Operating Environment

FIG. 2 is a block diagram illustrating an environment 300 for operatinga mobile device 400, according to an example embodiment, for deployingand/or implementing the digital asset 160 sharing system and methodsdescribed herein. The mobile electronic device 400 may be any of avariety of types of devices, for example a cellular telephone, apersonal digital assistant (PDA), a Personal Navigation Device (PND), ahandheld computer, a tablet computer, a notebook computer, or other typeof movable device. The device 400 may interface via a connection 310with a communication network 320. Depending on the form of the mobileelectronic device 400, any of a variety of types of connections 310 andcommunication networks 320 may be used. The device 400 may furtherinterface with a satellite 370 via a link 360.

For example, the connection 310 may be Code Division Multiple Access(CDMA) connection, a Global System for Mobile communications (GSM)connection, or other type of cellular connection. Such connection 310may implement any of a variety of types of data transfer technology,such as Single Carrier Radio Transmission Technology (1×RTT),Evolution-Data Optimized (EVDO) technology, General Packet Radio Service(GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE)technology, or other data transfer technology. When such technology isemployed, the communication network 320 may include a cellular networkthat has a plurality of cell sites of overlapping geographic coverage,interconnected by cellular telephone exchanges. These cellular telephoneexchanges may be coupled to a network backbone, for example, the publicswitched telephone network (PSTN), a packet-switched data network, or toother types of networks.

In another example, the connection 310 may be Wireless Fidelity (Wi-Fi,IEEE 802.11x type) connection, a Worldwide Interoperability forMicrowave Access (WiMAX) connection, or another type of wireless dataconnection. In such an embodiment, the communication network 320 mayinclude one or more wireless access points coupled to a local areanetwork (LAN), a wide area network (WAN), the Internet, or otherpacket-switched data network.

In yet another example, the connection 310 may be a wired connection,for example an Ethernet link, and the communication network may be alocal area network (LAN), a wide area network (WAN), the Internet, orother packet-switched data network. Accordingly, a variety of differentconfigurations are expressly contemplated.

A plurality of servers 330 may be coupled via interfaces to thecommunication network 320, for example, via wired or wirelessinterfaces. These servers 330 may be configured to provide various typesof services to the mobile electronic device 400. For example, one ormore servers 330 may execute location based service (LBS) applications340, which interoperate with software executing on the device 400, toprovide LBS's to a user. LB S's may use knowledge of the device'slocation, and/or the location of other devices, to providelocation-specific information, recommendations, notifications,interactive capabilities, and/or other functionality to a user.Knowledge of the device's location, and/or the location of otherdevices, may be obtained through interoperation of the device 400 with alocation determination application 350 executing on one or more of theservers 330. Location information may also be provided by the device400, without use of a location determination application, such asapplication 350. In certain examples, the device 400 may have somelimited location determination capabilities that are augmented by thelocation determination application 350. The servers are coupled todatabase 390, which includes point of interest files 392, user placefiles 394, and location history files 396.

Example Mobile Device

FIG. 3 is a block diagram illustrating the mobile device 400, accordingto an example embodiment, for deploying and/or implementing the digitalasset 160 management and sharing system and methods described herein.The device 400 may include a processor 410. The processor 410 may be anyof a variety of different types of commercially available processorssuitable for mobile devices, for example, an XScale architecturemicroprocessor, a Microprocessor without Interlocked Pipeline Stages(MIPS) architecture processor, or another type of processor. A memory420, such as a Random Access Memory (RAM), a Flash memory, or other typeof memory, is typically accessible to the processor. The memory 420 maybe adapted to store an operating system (OS) 430, as well as applicationprograms 440, such as a mobile location enabled application that mayprovide LB S′s to a user. The processor 410 may be coupled, eitherdirectly or via appropriate intermediary hardware, to a display 450 andto one or more input/output (I/O) devices 460, such as a keypad, a touchpanel sensor, a microphone, etc. Similarly, in some embodiments, theprocessor 410 may be coupled to a transceiver 470 that interfaces withan antenna 490. The transceiver 470 may be configured to both transmitand receive cellular network signals, wireless data signals, or othertypes of signals via the antenna 490, depending on the nature of thedevice 400. In this manner, the connection 410 with the communicationnetwork 420 may be established. Further, in some configurations, a GPSreceiver 480 may also make use of the antenna 490 to receive GPSsignals.

Example Platform Architecture

FIG. 4 is a block diagram illustrating a network-based system 500 fordeploying and/or implementing the digital asset 160 sharing system andmethods described herein. In an embodiment, the system operates in realtime or near real-time. The block diagram depicting a client-serversystem 500, within which an example embodiment may be deployed isdescribed. A networked system 502, in the example forms a network-baseddigital asset 160 management and sharing system, provides server-sidefunctionality, via a network 504 (e.g., the Internet or Wide AreaNetwork (WAN)) to one or more clients 510, 512. FIG. 4 illustrates, forexample, a web client 506 (e.g., a browser, such as the InternetExplorer browser developed by Microsoft Corporation of Redmond,Washington State), and a programmatic client 508 executing on respectiveclient machines 510 and 512. In an example, the client machines 510 and512 may be in the form of a mobile device, such as mobile device 400.

An Application Programming Interface (API) server 514 and a web server516 are coupled to, and provide programmatic and web interfacesrespectively to, one or more application servers 518. The applicationservers 518 host one or more digital asset 160 sharing applications 520(in certain examples these computer program components are thosedescribed herein for the digital asset 160 sharing system 100),communication applications 522, and other sub-systems 532. Theapplication servers 518 are, in turn, shown to be coupled to one or moredatabase servers 524 that facilitate access to one or more databases526. In some examples, the application server 518 may access thedatabases 526 directly without the need for a database server 524.

The asset management and sharing applications 520 may provide a numberof asset management and sharing functions and services to users thataccess the networked system 502, as described otherwise herein. Thecommunication applications 522 may likewise provide a number ofcommunication services and functions to users, for example to interfacewith and send messages and data between various communicationapplications, including e-mail services, text messaging services,instant messaging services, or other communication services, such asmessaging through social media platforms. While the asset sharingapplications 520 and communication applications 522, and othersub-systems 532 are shown in FIG. 5 to all form part of the networkedsystem 502, it will be appreciated that, in alternative embodiments, theapplications 520 and 522 or others may form part of a service that isseparate and distinct from the networked system 502.

Further, while the system 500 shown in FIG. 4 employs a client-serverarchitecture, the present invention is of course not limited to such anarchitecture, and could equally well find application in a distributed,or peer-to-peer, architecture system, for example. The variousapplications 520, applications 522, and sub-system 532 could also beimplemented as standalone software programs, which do not necessarilyhave networking capabilities.

The web client 506 accesses the various asset management and sharingapplications 520, communication applications 522, and optionalsub-systems 532 via the web interface supported by the web server 516.Similarly, the programmatic client 508 accesses the various services andfunctions provided by the applications, servers 520, 522 and 532 via theprogrammatic interface provided by the API server 514. The programmaticclient 508 may, for example, be a local recommendation smartphoneapplication to enable users to receive real-time location-aware merchantpromotions on their smartphones leveraging user profile data and currentlocation information provided by the smartphone.

FIG. 4 also illustrates a third party application 528, executing on athird party server machine 540, as having programmatic access to thenetworked system 502 via the programmatic interface provided by the APIserver 514. For example, the third party application 528 may, utilizinginformation retrieved from the networked system 502, support one or morefeatures or functions on a website hosted by the third party. The thirdparty website may, for example, provide one or more functions that aresupported by the relevant applications of the networked system 502.

Modules, Components and Logic

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules may constitute eithersoftware modules (e.g., code embodied on a machine-readable medium or ina transmission signal) or hardware modules. A hardware module is atangible unit capable of performing certain operations and may beconfigured or arranged in a certain manner. In example embodiments, oneor more computer systems (e.g., a standalone, client or server computersystem) or one or more hardware modules of a computer system (e.g., aprocessor or a group of processors) may be configured by software (e.g.,an application or application portion) as a hardware module thatoperates to perform certain operations as described herein.

In various embodiments, a hardware module may be implementedmechanically or electronically. For example, a hardware module maycomprise dedicated circuitry or logic that is permanently configured(e.g., as a special-purpose processor, such as a field programmable gatearray (FPGA) or an application-specific integrated circuit (ASIC)) toperform certain operations. A hardware module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that istemporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a hardware modulemechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations.

Accordingly, the term “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired) or temporarilyconfigured (e.g., programmed) to operate in a certain manner and/or toperform certain operations described herein. Considering embodiments inwhich hardware modules are temporarily configured (e.g., programmed),each of the hardware modules need not be configured or instantiated atany one instance in time. For example, where the hardware modulescomprise a general-purpose processor configured using software, thegeneral-purpose processor may be configured as respective differenthardware modules at different times. Software may accordingly configurea processor, for example, to constitute a particular hardware module atone instance of time and to constitute a different hardware module at adifferent instance of time.

Hardware modules may provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Wheremultiples of such hardware modules exist contemporaneously,communications may be achieved through signal transmission (e.g., overappropriate circuits and buses) that connect the hardware modules. Inembodiments in which multiple hardware modules are configured orinstantiated at different times, communications between such hardwaremodules may be achieved, for example, through the storage and retrievalof information in memory structures to which the multiple hardwaremodules have access. For example, one hardware module may perform anoperation, and store the output of that operation in a memory device towhich it is communicatively coupled. A further hardware module may then,at a later time, access the memory device to retrieve and process thestored output. Hardware modules may also initiate communications withinput or output devices, and may operate on a resource (e.g., acollection of information).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions. The modulesreferred to herein may, in some example embodiments, compriseprocessor-implemented modules.

Similarly, the methods described herein may be at least partiallyprocessor-implemented. For example, at least some of the operations of amethod may be performed by one or more processors orprocessor-implemented modules. The performance of certain of theoperations may be distributed among the one or more processors, not onlyresiding within a single machine, but deployed across a number ofmachines. In some example embodiments, the processor or processors maybe located in a single location (e.g., within a home environment, anoffice environment or as a server farm), while in other embodiments theprocessors may be distributed across a number of locations.

The one or more processors may also operate to support performance ofthe relevant operations in a “cloud computing” environment or as a“software as a service” (SaaS). For example, at least some of theoperations may be performed by a group of computers (as examples ofmachines including processors), these operations being accessible via anetwork (e.g., the Internet) and via one or more appropriate interfaces(e.g., Application Program Interfaces (APIs).)

Electronic Apparatus and System

Example embodiments may be implemented in digital electronic circuitry,or in computer hardware, firmware, software, or in combinations of them.Example embodiments may be implemented using a computer program product,e.g., a computer program tangibly embodied in an information carrier,e.g., in a machine-readable medium for execution by, or to control theoperation of, data processing apparatus, e.g., a programmable processor,a computer, or multiple computers.

A computer program may be written in any form of programming language,including compiled or interpreted languages, and it may be deployed inany form, including as a stand-alone program or as a module, subroutine,or other unit suitable for use in a computing environment. A computerprogram may be deployed to be executed on one computer or on multiplecomputers at one site or distributed across multiple sites andinterconnected by a communication network.

In example embodiments, operations may be performed by one or moreprogrammable processors executing a computer program to performfunctions by operating on input data and generating output. Methodoperations may also be performed by, and apparatus of exampleembodiments may be implemented as, special purpose logic circuitry,e.g., a field programmable gate array (FPGA) or an application-specificintegrated circuit (ASIC).

The computing system may include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. Inembodiments deploying a programmable computing system, it will beappreciated that both hardware and software architectures requireconsideration. Specifically, it will be appreciated that the choice ofwhether to implement certain functionality in permanently configuredhardware (e.g., an ASIC), in temporarily configured hardware (e.g., acombination of software and a programmable processor), or a combinationof permanently and temporarily configured hardware may be a designchoice. Below are set out hardware (e.g., machine) and softwarearchitectures that may be deployed, in various example embodiments.

Example Machine Architecture and Machine-Readable Medium

FIG. 5 is a block diagram of a machine in the example form of a computersystem 1000 within which instructions, for causing the machine toperform any one or more of the methodologies discussed herein, may beexecuted. In alternative embodiments, the machine operates as astandalone device or may be connected (e.g., networked) to othermachines. In a networked deployment, the machine may operate in thecapacity of a server or a client machine in server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine may be a personal computer (PC), atablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), acellular telephone, a web appliance, a network router, switch or bridge,or any machine capable of executing instructions (sequential orotherwise) that specify actions to be taken by that machine. Further,while only a single machine is illustrated, the term “machine” shallalso be taken to include any collection of machines that individually orjointly execute a set (or multiple sets) of instructions to perform anyone or more of the methodologies discussed herein.

The example computer system 1000 includes a processor 1002 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU) orboth), a main memory 1004 and a static memory 1006, which communicatewith each other via a bus 1008. The computer system 1000 may furtherinclude a video display unit 1010 (e.g., a liquid crystal display (LCD)or a cathode ray tube (CRT)). The computer system 1000 also includes analphanumeric input device 1012 (e.g., a keyboard), a user interface (UI)navigation device 1014 (e.g., a mouse), a disk drive unit 1016, a signalgeneration device 1018 (e.g., a speaker) and a network interface device1020.

Machine-Readable Medium

The disk drive unit 1016 includes a machine-readable medium 1022 onwhich is stored one or more sets of instructions and data structures(e.g., software) 1024 embodying or used by any one or more of themethodologies or functions described herein. The instructions 1024 mayalso reside, completely or at least partially, within the main memory1004 and/or within the processor 1002 during execution thereof by thecomputer system 1000, the main memory 1004 and the processor 1002 alsoconstituting machine-readable media.

While the machine-readable medium 1022 is shown in an example embodimentto be a single medium, the term “machine-readable medium” may include asingle medium or multiple media (e.g., a centralized or distributeddatabase, and/or associated caches and servers) that store the one ormore instructions or data structures. The term “machine-readable medium”shall also be taken to include any tangible medium that is capable ofstoring, encoding or carrying instructions for execution by the machineand that cause the machine to perform any one or more of themethodologies of the present invention, or that is capable of storing,encoding or carrying data structures used by or associated with suchinstructions. The term “machine-readable medium” shall accordingly betaken to include, but not be limited to, solid-state memories, andoptical and magnetic media. Specific examples of machine-readable mediainclude non-volatile memory, including by way of example semiconductormemory devices, e.g., Erasable Programmable Read-Only Memory (EPROM),Electrically Erasable Programmable Read-Only Memory (EEPROM), and flashmemory devices; magnetic disks such as internal hard disks and removabledisks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

Transmission Medium

The instructions 1024 may further be transmitted or received over acommunications network 1026 using a transmission medium. Theinstructions 1024 may be transmitted using the network interface device1020 and any one of a number of well-known transfer protocols (e.g.,HTTP). Examples of communication networks include a local area network(“LAN”), a wide area network (“WAN”), the Internet, mobile telephonenetworks, Plain Old Telephone (POTS) networks, and wireless datanetworks (e.g., WiFi and WiMax networks). The term “transmission medium”shall be taken to include any intangible medium that is capable ofstoring, encoding or carrying instructions for execution by the machine,and includes digital or analog communications signals or otherintangible media to facilitate communication of such software.

Thus, a method and system for computer guided asset management andsharing have been described. Although the present invention has beendescribed with reference to specific example embodiments, it will beevident that various modifications and changes may be made to theseembodiments without departing from the broader scope of the invention.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

Although an embodiment has been described with reference to specificexample embodiments, it will be evident that various modifications andchanges may be made to these embodiments without departing from thebroader scope of the invention. Accordingly, the specification anddrawings are to be regarded in an illustrative rather than a restrictivesense. The accompanying drawings that form a part hereof, show by way ofillustration, and not of limitation, specific embodiments in which thesubject matter may be practiced. The embodiments illustrated aredescribed in sufficient detail to enable those skilled in the art topractice the teachings disclosed herein. Other embodiments may be usedand derived therefrom, such that structural and logical substitutionsand changes may be made without departing from the scope of thisdisclosure. This Detailed Description, therefore, is not to be taken ina limiting sense, and the scope of various embodiments is defined onlyby the appended claims, along with the full range of equivalents towhich such claims are entitled.

Such embodiments of the inventive subject matter may be referred toherein, individually and/or collectively, by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed. Thus, although specific embodiments havebeen illustrated and described herein, it should be appreciated that anyarrangement calculated to achieve the same purpose may be substitutedfor the specific embodiments shown. This disclosure is intended to coverany and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart upon reviewing the above description.

All publications, patents, and patent documents referred to in thisdocument are incorporated by reference herein in their entirety, asthough individually incorporated by reference. In the event ofinconsistent usages between this document and those documents soincorporated by reference, the usage in the incorporated reference(s)should be considered supplementary to that of this document; forirreconcilable inconsistencies, the usage in this document controls.

In this document, the terms “a” or “an” are used, as is common in patentdocuments, to include one or more than one, independent of any otherinstances or usages of “at least one” or “one or more.” In thisdocument, the term “or” is used to refer to a nonexclusive or, such that“A or B” includes “A but not B,” “B but not A,” and “A and B,” unlessotherwise indicated. In the appended claims, the terms “including” and“in which” are used as the plain-English equivalents of the respectiveterms “comprising” and “wherein.” Also, in the following claims, theterms “including” and “comprising” are open-ended, that is, a system,device, article, or process that includes elements in addition to thoselisted after such a term in a claim are still deemed to fall within thescope of that claim. Moreover, in the following claims, the terms“first,” “second,” and “third,” etc. are used merely as labels, and arenot intended to impose numerical requirements on their objects.

The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b), requiring an abstract that will allow the reader to quicklyascertain the nature of the technical disclosure. It is submitted withthe understanding that it will not be used to interpret or limit thescope or meaning of the claims. In addition, in the foregoing DetailedDescription, it may be seen that various features are grouped togetherin a single embodiment for the purpose of streamlining the disclosure.This method of disclosure is not to be interpreted as reflecting anintention that the claimed embodiments require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive subject matter lies in less than all features of asingle disclosed embodiment. Thus the following claims are herebyincorporated into the Detailed Description, with each claim standing onits own as a separate embodiment.

What is claimed is:
 1. A digital asset localization system, the systemcomprising: at least one processor; and memory including instructionsthat, when executed by the at least one processor, cause the at leastone processor to: receive a digital asset provided by a provider;receive a digital asset build rules from a plurality of clientorganizations, wherein a digital asset build rule includes a localizeddigital asset building rule and organization information related to acorresponding one of the plurality of client organizations forincorporation into a localized digital asset; build a localized digitalasset using the digital asset and the digital asset build rule; andauthorize, by a host organization that is not one of the provider andthe plurality of client organizations, the provider and the plurality ofclient organizations access to the digital asset localization system. 2.The system of claim 1, wherein the instructions cause the at least oneprocessor to: receive a specification, from a first client organization,for a digital asset build rule using a template provided by a secondclient organization.
 3. The system of claim 2, wherein the instructionscause the at least one processor to: receive a template provided by atleast one of the provider and the plurality of client organizations. 4.The system of claim 3, wherein the instructions cause the at least oneprocessor to: authorize access and use of a digital asset provided bythe provider and the plurality of client organizations to the providerand the plurality of client organizations.
 5. The system of claim 1,wherein the instructions cause the at least one processor to: authorizeaccess, to the digital asset, for at least two or more of the providerand the plurality of client organizations.
 6. The system of claim 1,wherein the instructions cause the at least one processor to: receivedigital assets and digital asset build rules provided by the provider,wherein the digital asset build rules are configured to localize thedigital assets.
 7. At least one non-transitory computer readable mediumincluding instructions for digital asset localization, the instructions,when executed by a machine, cause the machine to: receive a digitalasset provided by a provider; receive digital asset build rules from aplurality of client organizations, wherein a digital asset build ruleincludes a localized digital asset building rule and organizationinformation related to a corresponding one of the plurality of clientorganizations for incorporation into a localized digital asset; build alocalized digital asset using the digital asset and the digital assetbuild rule; and authorize, by a host organization that is not one of theprovider and the plurality of client organizations, the provider and theplurality of client organizations access to the machine.
 8. The at leastone computer readable medium of claim 7, further comprising instructionsto: receive a specification, from a first client organization, for adigital asset build rule using a template provided by a second clientorganization.
 9. The at least one computer readable medium of claim 8,further comprising instructions to: receive a template provided by atleast one of the provider and the plurality of client organizations. 10.The at least one computer readable medium of claim 9, further comprisinginstructions to: authorize access and use of a digital asset provided bythe provider and the plurality of client organizations to the providerand the plurality of client organizations.
 11. The at least one computerreadable medium of claim 7, further comprising instructions to:authorize access, to the digital asset, for at least two or more of theprovider and the plurality of client organizations.
 12. The at least onecomputer readable medium of claim 7, further comprising instructions to:receive digital assets and digital asset build rules provided by theprovider, wherein the digital asset build rules are configured tolocalize the digital assets.
 13. A method for digital assetlocalization, the method comprising: receiving, at a computing system, adigital asset provided by a provider; receiving, at the computingsystem, digital asset build rules from a plurality of clientorganizations, wherein a digital asset build rule includes a localizeddigital asset building rule and organization information related to acorresponding one of the plurality of client organizations forincorporation into a localized digital asset; building, at the computingsystem, a localized digital asset using the digital asset and thedigital asset build rule; and authorizing, by a host organization thatis not one of the provider and the plurality of client organizations,the provider and the plurality of client organizations access to thecomputing system.
 14. The method of claim 13, comprising: receiving aspecification, from a first client organization, for a digital assetbuild rule using a template provided by a second client organization.15. The method of claim 14, comprising: receiving a template provided byat least one of the provider and the plurality of client organizations.16. The method of claim 15, comprising: authorizing access and use of adigital asset provided by the provider and the plurality of clientorganizations to the provider and the plurality of client organizations.17. The method of claim 13, comprising: authorizing access, to thedigital asset, for at least two or more of the provider and theplurality of client organizations.
 18. The method of claim 13,comprising: receiving digital assets and digital asset build rulesprovided by the provider, wherein the digital asset build rules areconfigured to localize the digital assets.